Knowledge Technology
Software Products

Knowledge Technology supplies a wide range of Data Communications Software Products, and can provide installation and support services for all of these products.

ICL Communications

Knowledge Technology produces ICL Communications packages for a wide range of hardware/operating system combinations. Although the platform may vary, the features provided by the products do not.

A full screen emulation of ICL's screen-mode (7561) terminal is provided allowing access to ICL VME hosts.

The VT52 and VT220+ emulations in the Windows and Macintosh products allow access to ICL DRS equipment running applications such as OfficePower, as well as other manufacturers' hosts, for example Unisys and Bull. The UNIX products include a transparent emulation providing access to other UNIX systems.

Both an FTF initiator and an FTF responder implementing ICL's File Transfer protocol (NIFTP-B(80)) are included in the packages.

The Direct Print responder can receive and process print spooler output for a number of different printer locations, and route the data to the appropriate printer.

Terminal Emulation Packages

Teemtalk, Termite and Legato have been added to the existing Doslan package in our range of Windows Terminal Emulators. All of these products support the ICL 7561 terminal emulation, and between them provide a wide range of features, emulations and protocol stacks. Contact Knowledge Technology for impartial advice on which package best suits your requirements.

Software Distribution

The benefits of Home-Working and Remote Computing in general have gained considerable publicity. However, the problem of updating software on widely dispersed computers has not been given the same prominence. The DistribuLink package can update automatically remote DOS/Windows and UNIX systems over PSTN, ISDN, X.25 and TCP/IP networks. With even a small number of remote users, DistribuLink will pay for itself very quickly indeed.

Sunlink

Knowledge Technology is the distributor for the SunLink range of OSI software. This range includes X.25, FTAM and X.400 as well as other OSI applications. These products complement Knowledge Technology's range of ICL communications software for Solaris.

Transport Drivers

Knowledge Technology supplies ISO Transport Driver for DOS and various flavours of Windows. The Transport Drivers are complemented by an API which simplifies application development.

ICL Communications

Knowledge Technology supplies ICL communications software for the following:
Windows
Doslan for Windows

Solaris 1 and 2
IPALink, OpenHost and OpenPrint

SCO UNIX
OpenLink/SCO, OpenHost/SCO and OpenPrint/SCO

Knowledge Technology supplies ISO Transport Drivers for DOS and various flavours of Windows. The Transport Drivers are complemented by an API which simplifies application development.

Transport Drivers

Overview

The Knowledge Technology ISO Transport Stack was conceived as a cross-platform package to support the OpenLink range of ICL connectivity products for DOS, Windows, Macintosh and UNIX. It has proved so successful that it is now provided on an OEM basis to support third-party OSI applications.
Variants of the Transport Stack are available which comply with the industry-standard NDIS and ODI interfaces. This allows the Transport operate over most manufacturers' Ethernet cards. Indeed, 3Com recommends the Knowledge Technology Transport Stack as the replacement for the ubiquitous Isolan MPS Transport.

Standards

The Knowledge Technology ISO Transport Stack complies with the following:

Modular Flexibility

The Knowledge Technology ISO Transport Stack has been designed as Network, Transport and User Interface modules. This allows third parties to choose the interface most appropriate to the application. Also, this allows the re-use of proven code when the package is ported to new environments. Substitution of different network and user interfaces has already proved to be straightforward.

Multi-Protocol Support

By complying with industry-standard interfaces, the Knowledge Technology ISO Transport Stack will operate alongside other protocols such as TCP/IP, DEC LAT, Novell and LAN Manager. This makes the package ideal for incorporation into existing multi-protocol host access products.


Doslan for Windows

Overview

Doslan for Windows is the complete ICL communications package for Windows PCs. It provides full IPA3 connectivity over the OSLAN Local Area Network to both ICL VME and UNIX hosts. Doslan for Windows is an approved Windows application.

A full screen emulation of ICL's screen-mode (7561) terminal is provided allowing access to ICL VME hosts. The VT52 and VT220+ emulations allow access to ICL DRS equipment running applications such as OfficePower, as well as other manufacturers' hosts, for example Unisys and Bull.

Both an FTF initiator and an FTF responder implementing ICL's File Transfer protocol (NIFTP-B(80)) are included in the package.

The Direct Print responder can receive and process print spooler output for a number of different printer locations, and route the data to the appropriate printer.

Also available separately is an ADI interface.

Doslan for Windows utilises an ISO Transport Service designed to run over the MPS, NDIS and ODI industry standard drivers. Doslan for Windows is unique in operating over all these drivers, allowing use alongside most other LAN applications on most manufacturers' Ethernet cards.

RSA Terminal connections

Doslan for Windows' 7561 terminal emulation provides a full 25-line emulation of ICL's screen-mode terminal by implementing ICL's ICAB-02 protocol. This emulation includes scalable fonts, the ability to assign strings to PC function keys, and to redefine the use of the keys on the PC keyboard, giving complete flexibility.
Any number of concurrent terminal sessions are supported to a mixture of host types with each session in a separate window. All the normal Windows functions such as cut-and paste are supported.

DRS Terminal connections

Connections to ICL's DRS equipment are provided by the VT52 and VT220+ emulations, which are included in Doslan for Windows. These can equally well be used to connect to any manufacturers' host which supports ISO Transport over Ethernet, for example Unisys and Bull. The emulations are complete implementations, including printer support.
The VT220+ emulation (also known as VT220 Doc 18) is provided specifically to allow Doslan for Windows users to access ICL's OfficePower package. Full support for the special OfficePower keys such as Accept, Reject and Exit is provided, as well as support for the numeric and cursor key-pads.

File Transfer

ICL's File Transfer protocol (NIFTP-B(80)) is implemented as both an initiator and a responder. The initiator is invokable from a user-friendly window, with separate windows for access to more advanced options. Once started the file transfer initiator runs in background leaving the user free to perform other tasks. Text and binary file transfers are supported in either direction.
The responder is also invoked via a user-friendly window, and runs in background sending and receiving files on the user's behalf. The responder supports the Take Job Input and Take Job Output options, allowing files to be executed or printed on receipt.

IPALink

Overview

IPALink is the complete ICL communications package for Sun SPARC stations running Solaris 1 and Solaris 2. It provides full IPA3 connectivity over Wide and Local Area Networks to both ICL VME and UNIX hosts.

RSA terminal connections are provided via a full screen emulation of ICL's screen-mode (7561) terminal. Terminal connections to other UNIX equipment are also available.
Both an FTF initiator and an FTF responder implementing ICL's File Transfer protocol (NIFTP-B(80)) are included in the package.

The Direct Print responder can receive and process print spooler output for a number of different printer locations, and route the data to the appropriate printer.
Also available separately is an ADI interface.

IPALink utilises the SunLink OSI or SunLink X.25 packages to provide the lower level connections, allowing IPALink to run alongside other products that use these standard packages. These packages are available from Knowledge Technology.

RSA Terminal connections


The RSA terminal connection program (rsa_connect) provides a full screen emulation of ICL's screen-mode (7561) terminal by implementing ICL's ICAB-02 protocol. By using the term_info file, rsa_connect will work with any terminal, including a Sun View window or a VT100.

A keyboard configuration file allows the user complete control of the keyboard's operation. Over 40 functions, some of which are not available on ICL terminals, can be assigned to a character or sequence of characters. This allows a function to be assigned to any key on the keyboard.

UNIX Terminal connections

A UNIX connection program (tty_connect) is provided in the IPALink package. This allows a transparent terminal connection to another UNIX platform. In this way, a telnet type of connection can be made over ISO protocols.

File Transfer

ICL's File Transfer protocol (NIFTP-B(80)) is implemented as both an initiator and a responder. The initiator is invokable from the command line, and transfers can be processed immediately, or submitted for batch processing in background. Text and binary file transfers are supported in either direction.

The responder will normally run as a daemon sending and receiving files on all users' behalf. Normal UNIX security measures are implemented, requiring the initiating entity to supply a user-name and password in order to access any area of the file-store. The responder supports the Take Job Input and Take Job Output options, allowing files to be executed or printed on receipt.

Printing

IPALink's print responder will normally run as a daemon listening for print requests on a specific Transport address (TSAP). A number of print responders may be started, listening on different addresses, and appearing to the host as multiple print locations.
Each responder can be configured to use its own UNIX command (usually lp) to process print spooler output. These commands can be used to route the data to the appropriate printer, or for more complex processing if required.

Open Systems Connectivity

IPALink utilises Sun's own SunLink OSI or SunLink X.25 packages to provide the network and transport layer facilities. This allows IPALink to run alongside other products that use these standard packages. SunLink OSI and SunLink X.25 can be configured to provide the following connection methods:

UNIX Flexibility

IPALink will provide peer-to-peer connectivity from a stand-alone SPARC station, or act as a gateway for any terminal or workstation. This allows one installation of IPALink to satisfy the ICL connectivity requirements of a number of users.

The number of connections is controlled by a licence file. This restricts the number of connections, not the number of users. That is, IPALink with an eight user licence can service far more than eight users, but they can make only eight connections between them. The IPALink software is identical for all licence sizes, which allows upgrades to be performed simply by changing the licence file. IPALink is available with single (actually two), eight, 16, 32 and 64 connection licences.

IPALink uses the term_info file to determine the capability of the terminal equipment accessing it. In this way, any type of terminal can be accommodated, including those without 25-line support. IPALink will display the top or bottom portion of the screen depending on the position of the cursor. If the cursor is moved (by the user or host) into the non-displayed portion of the screen, IPALink will scroll the screen accordingly. In addition, the keyboard configuration file allows full control of the keyboard's operation.

ICL Security

All IPALink's configuration is via ASCII plain-text files. These allow the system manager complete control over the addressing information used by IPALink. Access to these files can of course be restricted by the standard UNIX mechanisms.

The local address file allows the calling address capabilities of each user to be specified. This can be used to force a particular user to use a specific calling address which can be mapped onto a device mnemonic at the host. In this way, there can be a one-to-one mapping between a user-name on the Sun and a device mnemonic on the host.

The remote address file allows a symbolic name to be associated with the full address of a service. This symbolic name is then used on the command line instead of the full address. These names can be used on all three command line invokable programs; that is rsa_connect, tty_connect and ftf_init (the file transfer initiator). The format of the called address file allows the same name to be used to mean a different address to the different programs. For example, 3980VME can be used to both rsa_connect and ftf_init, even though the TSAPs for RSA terminal access and File Transfer are different.

OpenHost and OpenPrint

Overview

OpenHost and OpenPrint are a complementary pair of products which can be used individually, or together. OpenHost provides the ability for Sun SPARC equipment to accept incoming character-based terminal connections using OSI protocols over Wide and Local Area Networks. OpenPrint allows print output to be directed to asynchronous printers attached to OSLAN terminal servers (OSLUs), DRS 300s or X.25 terminal servers (PADs). Both products are available for Solaris 1 and Solaris 2.
OpenHost and OpenPrint utilise Sun's own SunLink OSI or SunLink X.25 packages to provide the network and transport layer facilities. This allows both programs to run alongside other products that use these standard packages. These packages are available from Knowledge Technology. SunLink OSI and SunLink X.25 can be configured to provide the following connection methods:

OpenHost

The OpenHost program normally runs as a daemon listening on a particular address for incoming connections. Naturally, a number of daemons may be started, listening on different addresses, or different networks. When an incoming connection is received, a pseudo-terminal is generated and a login process spawned to allow the user to log in.
If the user logs out the connection will be cleared automatically. Alternatively, of the user clears the call from the terminal end then the Sun processes are tidied-up.

OpenPrint

The OpenPrint program can be run in one of two ways. The simplest way to invoke it from the command line. In this case a connection will be made to the printer, and the contents of the file sent on the connection.
A more elegant method is to associate the program with a printer device. In this way the normal print command can be used, and the file is spooled in background. A number of remote printers can be set up in this way, all identified by a device id.

Terminal Flexibility

Because of the Open Systems design philosophy both products will operate with a variety of equipment and connection methods:
OpenHost is accessible from terminals on all ISO Transport terminal servers including OSNET terminal servers (OSLUs) and gateways. OpenPrint is capable of printing to asynchronous printers on these devices.

DRS equipment running UNIX or CDOS can connect to OpenHost.
Sun SPARC equipment running Knowledge Technology's IPALink package can interface with OpenHost and OpenPrint. Indeed, they are often supplied for use together. The tty_connect program can connect into OpenHost, and the dp_resp program can receive OpenPrint output.

Knowledge Technology's Doslan and Doslan for Windows products for PCs and MacPower product for Macintosh computers will work in a similar way to IPALink.

Terminals and printers attached to Triple-X PADs can connect to OpenHost and receive from OpenPrint respectively.

OpenLink/SCO

Overview

OpenLink/SCO is the complete ICL communications package for SCO UNIX. It provides full IPA3 connectivity over Wide and Local Area Networks to both ICL VME and UNIX hosts.

RSA terminal connections are provided via a full screen emulation of ICL's screen-mode (7561) terminal. Terminal connections to other UNIX equipment are also available.
Both an FTF initiator and an FTF responder implementing ICL's File Transfer protocol (NIFTP-B(80)) are included in the package.

The Direct Print responder can receive and process print spooler output for a number of different printer locations, and route the data to the appropriate printer.

Also available separately is an ADI interface.

OpenLink/SCO utilises the LAN Transport for SCO package to provide the Local Area Network connections, and Eicon Technology's X.25 and Transport packages to provide the Wide Area Network connections. This allows OpenLink/SCO to run alongside other products that use these standard packages.

RSA Terminal connections

The RSA terminal connection program (rsa_connect) provides a full screen emulation of ICL's screen-mode terminal by implementing ICL's ICAB-02 protocol. By using the term_info file, rsa_connect will work with any terminal, including a Wyse or a VT100.
A keyboard configuration file allows the user complete control of the keyboard's operation. Over 40 functions, some of which are not available on ICL terminals, can be assigned to a character or sequence of characters. This allows a function to be assigned to any key on the keyboard.

UNIX Terminal connections

A UNIX connection program (tty_connect) is provided in the OpenLink/SCO package. This allows a transparent terminal connection to another UNIX platform. In this way, an telnet type of connection can be made over ISO protocols.

File Transfer

ICL's File Transfer protocol (NIFTP-B(80)) is implemented as both an initiator and a responder. The initiator is invokable from the command line, and transfers can be processed immediately, or submitted for batch processing in background. Text and binary file transfers are supported in either direction.

The responder will normally run as a daemon sending and receiving files on all users' behalf. Normal UNIX security measures are implemented, requiring the initiating entity to supply a user-name and password in order to access any area of the file-store. The responder supports the Take Job Input and Take Job Output options, allowing files to be executed or printed on receipt.

Printing

OpenLink/SCO's print responder will normally run as a daemon listening for print requests on a specific Transport address (TSAP). A number of print responders may be started, listening on different addresses, and appearing to the host as multiple print locations.

Each responder can be configured to use its own UNIX command (usually lp) to process print spooler output. These commands can be used to route the data to the appropriate printer, or for more complex processing if required.

Open Systems Connectivity

OpenLink/SCO utilises the LAN Transport for SCO package or the Eicon Technology OSI PC Gateway for SCO package to provide the network and transport layer facilities. These allow OpenLink/SCO to run alongside other products that use these standard package. LAN Transport for SCO can be configured to provide the following connection methods:

UNIX Flexibility

OpenLink/SCO will provide peer-to-peer connectivity from a stand-alone SCO UNIX station, or act as a gateway for any terminal or workstation. This allows one installation of OpenLink/SCO to satisfy the ICL connectivity requirements of a number of users.

The number of connections is controlled by a licence file. This restricts the number of connections, not the number of users. That is, OpenLink/SCO with an eight user licence can service far more than eight users, but they can make only eight connections between them. The OpenLink/SCO software is identical for all licence sizes, which allows upgrades to be performed simply by changing the licence file. OpenLink/SCO is available with single (actually two), eight, 16, 32 and 64 connection licences.

OpenLink/SCO uses the term_info file to determine the capability of the terminal equipment accessing it. In this way, any type of terminal can be accommodated, including those without 25-line support. OpenLink/SCO will display the top or bottom portion of the screen depending on the position of the cursor. If the cursor is moved (by the user or host) into the non-displayed portion of the screen, OpenLink/SCO will scroll the screen accordingly. In addition, the keyboard configuration file allows full control of the keyboard's operation.

ICL Security

All OpenLink/SCO's configuration is via ASCII plain-text files. These allow the system manager complete control over the addressing information used by OpenLink/SCO. Access to these files can of course be restricted by the standard UNIX mechanisms.

The local address file allows the calling address capabilities of each user to be specified. This can be used to force a particular user to use a specific calling address which can be mapped onto a device mnemonic at the host. In this way, there can be a one-to-one mapping between a user-name on the SCO system and a device mnemonic on the host.

The remote address file allows a symbolic name to be associated with the full address of a service. This symbolic name is then used on the command line instead of the full address. These names can be used on all three command line invokable programs; that is rsa_connect, tty_connect and ftf_init (the file transfer initiator). The format of the called address file allows the same name to be used to mean a different address to the different programs. For example, 3980VME can be used to both rsa_connect and ftf_init, even though the TSAPs for RSA terminal access and File Transfer are different.

OpenHost/SCO and OpenPrint/SCO

Overview

OpenHost and OpenPrint are a complementary pair of products which can be used individually, or together. OpenHost provides the ability for SCO UNIX equipment to accept incoming character-based terminal connections using OSI protocols over a Local Area Network. OpenPrint allows print output to be directed to asynchronous printers attached to OSLAN terminal servers (OSLUs) or X.25 terminal servers (PADs).
OpenHost and OpenPrint utilise the LAN Transport for SCO package to provide the Local Area Network connections, and Eicon Technology's OSI PC Gateway for SCO package to provide the Wide Area Network connections. This allows both programs to run alongside other products that use these standard packages.

OpenHost

The OpenHost program normally runs as a daemon listening on a particular address for incoming connections. Naturally, a number of daemons may be started, listening on different addresses, or different networks. When an incoming connection is received, a pseudo-terminal is generated and a login process spawned to allow the user to log in.
If the user logs out the connection will be cleared automatically. Alternatively, of the user clears the call from the terminal end then the SCO UNIX processes are tidied-up.

OpenPrint

The OpenPrint program can be run in one of two ways. The simplest way to invoke it from the command line. In this case a connection will be made to the printer, and the contents of the file sent on the connection.

A more elegant method is to associate the program with a printer device in the print_cap file. In this way the normal lp command can be used, and the file is spooled in background. A number of remote printers can be set up in this way, all identified by a device id.

Terminal Flexibility

Because of the Open Systems design philosophy both products will operate with a variety of equipment and connection methods:

OpenHost is accessible from terminals on all ISO Transport terminal servers including OSNET terminal servers (OSLUs) and gateways. OpenPrint is capable of printing to asynchronous printers on these devices.

DRS equipment running UNIX or CDOS can connect to OpenHost.
SCO UNIX equipment running Knowledge Technology's OpenLink package can interface with OpenHost and OpenPrint. Indeed, they are often supplied for use together. The tty_connect program can connect into OpenHost, and the dp_resp program can receive OpenPrint output.

Knowledge Technology's Doslan and Doslan for Windows products for PCs and MacVME product for Macintoshes will work in a similar way to OpenLink.

Terminals and printers attached to Triple-X PADs can connect to OpenHost and receive from OpenPrint respectively.



The Knowledge Group


Knowledge House, Concorde Road, Patchway, Bristol, BS12 5TW
Tel: 0117 900 7500
Fax: 0117 900 7501
Email: sales@ktgroup.co.uk